From e5ad3abfb2c49676a64273132c3380e22f313017 Mon Sep 17 00:00:00 2001 From: "awilliam@xenbuild.aw" Date: Mon, 6 Mar 2006 09:09:18 -0700 Subject: [PATCH] [IA64] #if 0'd useless code in timer handled. Signed-off-by: Tristan Gingold --- xen/arch/ia64/xen/xentime.c | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/xen/arch/ia64/xen/xentime.c b/xen/arch/ia64/xen/xentime.c index 79fe235633..3ce3dfbf26 100644 --- a/xen/arch/ia64/xen/xentime.c +++ b/xen/arch/ia64/xen/xentime.c @@ -116,6 +116,12 @@ xen_timer_interrupt (int irq, void *dev_id, struct pt_regs *regs) } #endif #endif + +#if 0 + /* Nobody seems to be able to explain this code. + It seems to be accumulated tricks, which are not required anymore. + Also I have made many tests, I'd like to get confirmation from + other site (TG). */ if (current->domain == dom0) { // FIXME: there's gotta be a better way of doing this... // We have to ensure that domain0 is launched before we @@ -130,6 +136,7 @@ xen_timer_interrupt (int irq, void *dev_id, struct pt_regs *regs) vcpu_wake(dom0->vcpu[0]); } } +#endif if (!is_idle_domain(current->domain)) { if (vcpu_timer_expired(current)) { vcpu_pend_timer(current); -- 2.30.2